Skip to content

Claude code guide #1337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 46 commits into
base: main
Choose a base branch
from
Open

Claude code guide #1337

wants to merge 46 commits into from

Conversation

serverless-mom
Copy link
Contributor

Affected Components

  • Content & Marketing
  • Pricing
  • Test
  • Docs
  • Learn
  • Other

This guide takes a slightly conservative path through using Claude code for PWT, starting with a codegen test as a model. This path has had good, consistent results for me.

Copy link

vercel bot commented Aug 1, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
checklyhq-com 🛑 Canceled Aug 14, 2025 4:35pm

@serverless-mom serverless-mom enabled auto-merge (squash) August 1, 2025 02:20
Copy link
Contributor

@sujaya-sys sujaya-sys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, added a few minor bits of feedback!

})
```

While you can deploy a Playwright check without a `.check.ts` configuration file, this isn't generally a good practice, as you should at least set the logical ID for your check.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a strong statement because it's baked into the checkly.config. However, I'm not sure if we should tell the story of our own options not being the best practice.


While you can deploy a Playwright check without a `.check.ts` configuration file, this isn't generally a good practice, as you should at least set the logical ID for your check.

### 2. Add our new Check to Claude's Context
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I won't die on this hill 🫣, but I still don't think this should be a recommendation because it doesn't scale. If we're vibing and we need to tell what to add to the context all the time that's a very manual approach. Having something like

Before creating more check files scan __checks__ for more info and base setup

is way more scalable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh that's smart. yeah I'll add something like:

Add another line to Claude's context in CLAUDE.md by entering:

# Before creating more check files scan `__checks__` for more info and base setup

@stefanjudis
Copy link
Collaborator

I've left some final niggles would love @Dgiordano33 to have the final saying though. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants